There were a number of changes in the tests between our copy of the hub and
that commit, so let's focus on the actual code fix instead of trying to play
the “backport the context” game.
Gbp-Pq: Name 0021-backport-sshd-session-support.patch
Adding the 0017 and 0018 patches had the side effect of uncovering
reliability issues in TestStreaming(). Let's not block the bugfix for
#1040976 on fixing that test: it's more important for the acquisition
bugfix to make its way into testing and into stable.
Gbp-Pq: Name 0019-disable-unreliable-test-TestStreaming.patch
mmetc [Tue, 27 Jun 2023 08:46:25 +0000 (10:46 +0200)]
[PATCH] non-fatal error if some datasource can't be run (i.e. journalctl but systemd is missing) (#2310)
This on the other hand, gives a new fatal error when there are no valid datasources.
In the previous version, crowdsec kept running with just a warning if no
acquisition yaml or dir were specified.
Gbp-Pq: Name 0018-non-fatal-errors-for-invalid-datasources.patch
Cyril Brulebois [Wed, 1 Mar 2023 21:36:00 +0000 (22:36 +0100)]
Silence yaml patching
Being able to patch configuration files using .local snippets is relatively new,
and very useful when it comes to shipping mostly untouched configuration files,
with just a few values set in a .local file.
Unfortunately the initial code is very chatty and generates info-level messages
in all cscli calls.
An early patch upstream is ca12432a2acd2fd607e9fbea97fea3fb3f124678 (backported
here), which demotes those messages from info to debug. It left the “Prepending”
messages at info, but those haven't been seen with the current packages, so
that's left untouched in this patch as well.
Further refinement landed in cd4dabde0ec833552881dd36780ab847cf20882d but that
touches more code, and we're closing in freeze-wise, so leave it alone. All our
crowdsec* packages ship a README.Debian file, which should be sufficient in most
cases. When in doubt, adjusting the log level in specific commands should be
enough to figure out what's happening.
Both aim at checking performance, and might error out when the underlying
system is “slow”. That was the case for the first test on arm64 (KO on
arm-arm-01, OK on arm-ubc-03) and on armel (KO on arm-ubc-06, OK on
arm-conova-02), and for the second test on mipsel (KO on mipsel-aql-02).
The same might happen on ci.debian.net, so disable both tests everywhere.
Manuel Sabban [Fri, 25 Nov 2022 07:34:47 +0000 (08:34 +0100)]
Refresh code generated from protobuf specifications
Without this patch, crowdsec would build fine but would fail in its testsuite,
reaching the 10-minute timeout. This was tracked down to unexpected csplugins
crashes, due to mismatched protobuf versions.
This issue would go away with golang-goprotobuf-dev 1.5.2-1~exp1 (as found in
experimental for a while) instead of 1.3.5-2 (in unstable as of November 2022).
Since protobuf's build-time and run-time are particularly tricky to get right,
incompatible 1.3.x and 1.5.x versions are packaged separately and aren't
co-installable. Since most packages depend on the 1.3.x version, it's not
possible to pull the 1.5.x version to avoid this issue.
Therefore, upstream was kind enough to come up with this patch, refreshing the
generated code so that it works fine within unstable.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0011-refresh-protobuf-code.patch
Cyril Brulebois [Mon, 1 Mar 2021 20:40:04 +0000 (20:40 +0000)]
Automatically enable the online hub
By default, crowdsec comes with an offline copy of the hub (see
README.Debian). When running `cscli hub update`, ensure switching from
this offline copy to the online hub.
To ensure cscli doesn't disable anything that was configured (due to
symlinks from /etc/crowdsec becoming dangling all of a sudden), copy the
offline hub in the live directory (/var/lib/crowdsec/hub), and let
further operations (`cscli hub upgrade`, or `cscli <type> install`)
update the live directory as required.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0007-automatically-enable-online-hub.patch
Cyril Brulebois [Fri, 22 Jan 2021 13:25:54 +0000 (13:25 +0000)]
Adjust systemd unit
- Adjust paths for the packaged crowdsec binary (/usr/bin).
- Drop commented out ExecStartPost entirely.
- Drop syslog.target dependency, it's socket-activated (thanks to the
systemd-service-file-refers-to-obsolete-target lintian tag).
- Ensure both local and online API credentials have been defined.
* Backport support for sshd-session (Closes: #1081196), with a focus
on the code (leaving the tests behind), and with thanks to Wang Jian
for the report, and Martin Dosch for tracking down the bugfix:
- 0021-backport-sshd-session-support.patch
Adding the 0017 and 0018 patches had the side effect of uncovering
reliability issues in TestStreaming(). Let's not block the bugfix for
#1040976 on fixing that test: it's more important for the acquisition
bugfix to make its way into testing and into stable.
Gbp-Pq: Name 0019-disable-unreliable-test-TestStreaming.patch
mmetc [Tue, 27 Jun 2023 08:46:25 +0000 (10:46 +0200)]
[PATCH] non-fatal error if some datasource can't be run (i.e. journalctl but systemd is missing) (#2310)
This on the other hand, gives a new fatal error when there are no valid datasources.
In the previous version, crowdsec kept running with just a warning if no
acquisition yaml or dir were specified.
Gbp-Pq: Name 0018-non-fatal-errors-for-invalid-datasources.patch
Cyril Brulebois [Wed, 1 Mar 2023 21:36:00 +0000 (22:36 +0100)]
Silence yaml patching
Being able to patch configuration files using .local snippets is relatively new,
and very useful when it comes to shipping mostly untouched configuration files,
with just a few values set in a .local file.
Unfortunately the initial code is very chatty and generates info-level messages
in all cscli calls.
An early patch upstream is ca12432a2acd2fd607e9fbea97fea3fb3f124678 (backported
here), which demotes those messages from info to debug. It left the “Prepending”
messages at info, but those haven't been seen with the current packages, so
that's left untouched in this patch as well.
Further refinement landed in cd4dabde0ec833552881dd36780ab847cf20882d but that
touches more code, and we're closing in freeze-wise, so leave it alone. All our
crowdsec* packages ship a README.Debian file, which should be sufficient in most
cases. When in doubt, adjusting the log level in specific commands should be
enough to figure out what's happening.
Both aim at checking performance, and might error out when the underlying
system is “slow”. That was the case for the first test on arm64 (KO on
arm-arm-01, OK on arm-ubc-03) and on armel (KO on arm-ubc-06, OK on
arm-conova-02), and for the second test on mipsel (KO on mipsel-aql-02).
The same might happen on ci.debian.net, so disable both tests everywhere.
Manuel Sabban [Fri, 25 Nov 2022 07:34:47 +0000 (08:34 +0100)]
Refresh code generated from protobuf specifications
Without this patch, crowdsec would build fine but would fail in its testsuite,
reaching the 10-minute timeout. This was tracked down to unexpected csplugins
crashes, due to mismatched protobuf versions.
This issue would go away with golang-goprotobuf-dev 1.5.2-1~exp1 (as found in
experimental for a while) instead of 1.3.5-2 (in unstable as of November 2022).
Since protobuf's build-time and run-time are particularly tricky to get right,
incompatible 1.3.x and 1.5.x versions are packaged separately and aren't
co-installable. Since most packages depend on the 1.3.x version, it's not
possible to pull the 1.5.x version to avoid this issue.
Therefore, upstream was kind enough to come up with this patch, refreshing the
generated code so that it works fine within unstable.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0011-refresh-protobuf-code.patch
Cyril Brulebois [Mon, 1 Mar 2021 20:40:04 +0000 (20:40 +0000)]
Automatically enable the online hub
By default, crowdsec comes with an offline copy of the hub (see
README.Debian). When running `cscli hub update`, ensure switching from
this offline copy to the online hub.
To ensure cscli doesn't disable anything that was configured (due to
symlinks from /etc/crowdsec becoming dangling all of a sudden), copy the
offline hub in the live directory (/var/lib/crowdsec/hub), and let
further operations (`cscli hub upgrade`, or `cscli <type> install`)
update the live directory as required.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0007-automatically-enable-online-hub.patch
Cyril Brulebois [Fri, 22 Jan 2021 13:25:54 +0000 (13:25 +0000)]
Adjust systemd unit
- Adjust paths for the packaged crowdsec binary (/usr/bin).
- Drop commented out ExecStartPost entirely.
- Drop syslog.target dependency, it's socket-activated (thanks to the
systemd-service-file-refers-to-obsolete-target lintian tag).
- Ensure both local and online API credentials have been defined.
Adding the 0017 and 0018 patches had the side effect of uncovering
reliability issues in TestStreaming(). Let's not block the bugfix for
#1040976 on fixing that test: it's more important for the acquisition
bugfix to make its way into testing and into stable.
Gbp-Pq: Name 0019-disable-unreliable-test-TestStreaming.patch
mmetc [Tue, 27 Jun 2023 08:46:25 +0000 (10:46 +0200)]
[PATCH] non-fatal error if some datasource can't be run (i.e. journalctl but systemd is missing) (#2310)
This on the other hand, gives a new fatal error when there are no valid datasources.
In the previous version, crowdsec kept running with just a warning if no
acquisition yaml or dir were specified.
Gbp-Pq: Name 0018-non-fatal-errors-for-invalid-datasources.patch
Cyril Brulebois [Wed, 1 Mar 2023 21:36:00 +0000 (22:36 +0100)]
Silence yaml patching
Being able to patch configuration files using .local snippets is relatively new,
and very useful when it comes to shipping mostly untouched configuration files,
with just a few values set in a .local file.
Unfortunately the initial code is very chatty and generates info-level messages
in all cscli calls.
An early patch upstream is ca12432a2acd2fd607e9fbea97fea3fb3f124678 (backported
here), which demotes those messages from info to debug. It left the “Prepending”
messages at info, but those haven't been seen with the current packages, so
that's left untouched in this patch as well.
Further refinement landed in cd4dabde0ec833552881dd36780ab847cf20882d but that
touches more code, and we're closing in freeze-wise, so leave it alone. All our
crowdsec* packages ship a README.Debian file, which should be sufficient in most
cases. When in doubt, adjusting the log level in specific commands should be
enough to figure out what's happening.
Both aim at checking performance, and might error out when the underlying
system is “slow”. That was the case for the first test on arm64 (KO on
arm-arm-01, OK on arm-ubc-03) and on armel (KO on arm-ubc-06, OK on
arm-conova-02), and for the second test on mipsel (KO on mipsel-aql-02).
The same might happen on ci.debian.net, so disable both tests everywhere.
Manuel Sabban [Fri, 25 Nov 2022 07:34:47 +0000 (08:34 +0100)]
Refresh code generated from protobuf specifications
Without this patch, crowdsec would build fine but would fail in its testsuite,
reaching the 10-minute timeout. This was tracked down to unexpected csplugins
crashes, due to mismatched protobuf versions.
This issue would go away with golang-goprotobuf-dev 1.5.2-1~exp1 (as found in
experimental for a while) instead of 1.3.5-2 (in unstable as of November 2022).
Since protobuf's build-time and run-time are particularly tricky to get right,
incompatible 1.3.x and 1.5.x versions are packaged separately and aren't
co-installable. Since most packages depend on the 1.3.x version, it's not
possible to pull the 1.5.x version to avoid this issue.
Therefore, upstream was kind enough to come up with this patch, refreshing the
generated code so that it works fine within unstable.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0011-refresh-protobuf-code.patch
Cyril Brulebois [Mon, 1 Mar 2021 20:40:04 +0000 (20:40 +0000)]
Automatically enable the online hub
By default, crowdsec comes with an offline copy of the hub (see
README.Debian). When running `cscli hub update`, ensure switching from
this offline copy to the online hub.
To ensure cscli doesn't disable anything that was configured (due to
symlinks from /etc/crowdsec becoming dangling all of a sudden), copy the
offline hub in the live directory (/var/lib/crowdsec/hub), and let
further operations (`cscli hub upgrade`, or `cscli <type> install`)
update the live directory as required.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0007-automatically-enable-online-hub.patch
Cyril Brulebois [Fri, 22 Jan 2021 13:25:54 +0000 (13:25 +0000)]
Adjust systemd unit
- Adjust paths for the packaged crowdsec binary (/usr/bin).
- Drop commented out ExecStartPost entirely.
- Drop syslog.target dependency, it's socket-activated (thanks to the
systemd-service-file-refers-to-obsolete-target lintian tag).
- Ensure both local and online API credentials have been defined.
* Add a symlink to config/crowdsec.service from debian/, and drop it
from crowdsec.install, leaving it up to dh_installsystemd to choose
where to install it (Closes: #1054084).
Adding the 0017 and 0018 patches had the side effect of uncovering
reliability issues in TestStreaming(). Let's not block the bugfix for
#1040976 on fixing that test: it's more important for the acquisition
bugfix to make its way into testing and into stable.
Gbp-Pq: Name 0019-disable-unreliable-test-TestStreaming.patch
mmetc [Tue, 27 Jun 2023 08:46:25 +0000 (10:46 +0200)]
[PATCH] non-fatal error if some datasource can't be run (i.e. journalctl but systemd is missing) (#2310)
This on the other hand, gives a new fatal error when there are no valid datasources.
In the previous version, crowdsec kept running with just a warning if no
acquisition yaml or dir were specified.
Gbp-Pq: Name 0018-non-fatal-errors-for-invalid-datasources.patch
Cyril Brulebois [Wed, 1 Mar 2023 21:36:00 +0000 (22:36 +0100)]
Silence yaml patching
Being able to patch configuration files using .local snippets is relatively new,
and very useful when it comes to shipping mostly untouched configuration files,
with just a few values set in a .local file.
Unfortunately the initial code is very chatty and generates info-level messages
in all cscli calls.
An early patch upstream is ca12432a2acd2fd607e9fbea97fea3fb3f124678 (backported
here), which demotes those messages from info to debug. It left the “Prepending”
messages at info, but those haven't been seen with the current packages, so
that's left untouched in this patch as well.
Further refinement landed in cd4dabde0ec833552881dd36780ab847cf20882d but that
touches more code, and we're closing in freeze-wise, so leave it alone. All our
crowdsec* packages ship a README.Debian file, which should be sufficient in most
cases. When in doubt, adjusting the log level in specific commands should be
enough to figure out what's happening.
Both aim at checking performance, and might error out when the underlying
system is “slow”. That was the case for the first test on arm64 (KO on
arm-arm-01, OK on arm-ubc-03) and on armel (KO on arm-ubc-06, OK on
arm-conova-02), and for the second test on mipsel (KO on mipsel-aql-02).
The same might happen on ci.debian.net, so disable both tests everywhere.
Manuel Sabban [Fri, 25 Nov 2022 07:34:47 +0000 (08:34 +0100)]
Refresh code generated from protobuf specifications
Without this patch, crowdsec would build fine but would fail in its testsuite,
reaching the 10-minute timeout. This was tracked down to unexpected csplugins
crashes, due to mismatched protobuf versions.
This issue would go away with golang-goprotobuf-dev 1.5.2-1~exp1 (as found in
experimental for a while) instead of 1.3.5-2 (in unstable as of November 2022).
Since protobuf's build-time and run-time are particularly tricky to get right,
incompatible 1.3.x and 1.5.x versions are packaged separately and aren't
co-installable. Since most packages depend on the 1.3.x version, it's not
possible to pull the 1.5.x version to avoid this issue.
Therefore, upstream was kind enough to come up with this patch, refreshing the
generated code so that it works fine within unstable.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0011-refresh-protobuf-code.patch
Cyril Brulebois [Mon, 1 Mar 2021 20:40:04 +0000 (20:40 +0000)]
Automatically enable the online hub
By default, crowdsec comes with an offline copy of the hub (see
README.Debian). When running `cscli hub update`, ensure switching from
this offline copy to the online hub.
To ensure cscli doesn't disable anything that was configured (due to
symlinks from /etc/crowdsec becoming dangling all of a sudden), copy the
offline hub in the live directory (/var/lib/crowdsec/hub), and let
further operations (`cscli hub upgrade`, or `cscli <type> install`)
update the live directory as required.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0007-automatically-enable-online-hub.patch
Cyril Brulebois [Fri, 22 Jan 2021 13:25:54 +0000 (13:25 +0000)]
Adjust systemd unit
- Adjust paths for the packaged crowdsec binary (/usr/bin).
- Drop commented out ExecStartPost entirely.
- Drop syslog.target dependency, it's socket-activated (thanks to the
systemd-service-file-refers-to-obsolete-target lintian tag).
- Ensure both local and online API credentials have been defined.
Adding the 0017 and 0018 patches had the side effect of uncovering
reliability issues in TestStreaming(). Let's not block the bugfix for
#1040976 on fixing that test: it's more important for the acquisition
bugfix to make its way into testing and into stable.
Gbp-Pq: Name 0019-disable-unreliable-test-TestStreaming.patch
mmetc [Tue, 27 Jun 2023 08:46:25 +0000 (10:46 +0200)]
[PATCH] non-fatal error if some datasource can't be run (i.e. journalctl but systemd is missing) (#2310)
This on the other hand, gives a new fatal error when there are no valid datasources.
In the previous version, crowdsec kept running with just a warning if no
acquisition yaml or dir were specified.
Gbp-Pq: Name 0018-non-fatal-errors-for-invalid-datasources.patch
Cyril Brulebois [Wed, 1 Mar 2023 21:36:00 +0000 (22:36 +0100)]
Silence yaml patching
Being able to patch configuration files using .local snippets is relatively new,
and very useful when it comes to shipping mostly untouched configuration files,
with just a few values set in a .local file.
Unfortunately the initial code is very chatty and generates info-level messages
in all cscli calls.
An early patch upstream is ca12432a2acd2fd607e9fbea97fea3fb3f124678 (backported
here), which demotes those messages from info to debug. It left the “Prepending”
messages at info, but those haven't been seen with the current packages, so
that's left untouched in this patch as well.
Further refinement landed in cd4dabde0ec833552881dd36780ab847cf20882d but that
touches more code, and we're closing in freeze-wise, so leave it alone. All our
crowdsec* packages ship a README.Debian file, which should be sufficient in most
cases. When in doubt, adjusting the log level in specific commands should be
enough to figure out what's happening.
Both aim at checking performance, and might error out when the underlying
system is “slow”. That was the case for the first test on arm64 (KO on
arm-arm-01, OK on arm-ubc-03) and on armel (KO on arm-ubc-06, OK on
arm-conova-02), and for the second test on mipsel (KO on mipsel-aql-02).
The same might happen on ci.debian.net, so disable both tests everywhere.
Manuel Sabban [Fri, 25 Nov 2022 07:34:47 +0000 (08:34 +0100)]
Refresh code generated from protobuf specifications
Without this patch, crowdsec would build fine but would fail in its testsuite,
reaching the 10-minute timeout. This was tracked down to unexpected csplugins
crashes, due to mismatched protobuf versions.
This issue would go away with golang-goprotobuf-dev 1.5.2-1~exp1 (as found in
experimental for a while) instead of 1.3.5-2 (in unstable as of November 2022).
Since protobuf's build-time and run-time are particularly tricky to get right,
incompatible 1.3.x and 1.5.x versions are packaged separately and aren't
co-installable. Since most packages depend on the 1.3.x version, it's not
possible to pull the 1.5.x version to avoid this issue.
Therefore, upstream was kind enough to come up with this patch, refreshing the
generated code so that it works fine within unstable.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0011-refresh-protobuf-code.patch
Cyril Brulebois [Mon, 1 Mar 2021 20:40:04 +0000 (20:40 +0000)]
Automatically enable the online hub
By default, crowdsec comes with an offline copy of the hub (see
README.Debian). When running `cscli hub update`, ensure switching from
this offline copy to the online hub.
To ensure cscli doesn't disable anything that was configured (due to
symlinks from /etc/crowdsec becoming dangling all of a sudden), copy the
offline hub in the live directory (/var/lib/crowdsec/hub), and let
further operations (`cscli hub upgrade`, or `cscli <type> install`)
update the live directory as required.
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Gbp-Pq: Name 0007-automatically-enable-online-hub.patch
Cyril Brulebois [Fri, 22 Jan 2021 13:25:54 +0000 (13:25 +0000)]
Adjust systemd unit
- Adjust paths for the packaged crowdsec binary (/usr/bin).
- Drop commented out ExecStartPost entirely.
- Drop syslog.target dependency, it's socket-activated (thanks to the
systemd-service-file-refers-to-obsolete-target lintian tag).
- Ensure both local and online API credentials have been defined.
projects / crowdsec.git / log